Fixes #14

- Split up the reading of the file contents and the parsing of the JSON into 2 separate variables `fileContent` and `jsonContents` for ease in the `readJsonFile` util function.

- Added a null coalescing operator to the `jsonContents` variable to ensure the variable is always an empty object if the parsing function from `jsonc-parser` package returns `null`.

- Added a `jsonErrors` variable with a default of an empty array, and passed this variable as the optional param in the json `parse` method to collect the parse errors it encounters. We can then use this array to check if there's errors inside.

- Added new `constructJsonParseErrorMsg` util function (and added the function call to `readJsonFile`) to loop through the JSON parse error array and construct the error messages since the `jsonc-parser` package doesn't provide a proper error message itself, and only provides error codes and offsets.

For each of the parse errors we construct a message that includes:

    - A formatted error name obtained using the numeric error code
    - A line number calculated from the error's offset and length
    - A column number calculated from the error's offset

The messages are formatted like so:

`Error [error index] - [Error Name] at [filepath]:[line]:[column]`

The filepath format of `filepath:line:column` makes it easy to navigate to the specific place in the file for easier debugging.

- Added error handling so that it creates a new internal Error with a specific "Failed to parse..." error message. Then log the error stack to the Output Channel, which consists of the specific message, the parse error messages, and the stack trace of where in the extension it occurred.

Because `readJsonFile` is a make or break kinda function, we should notify the user by showing an error popup dialog.

- Added vscode's `showErrorMessage` method to tell the user that errors occurred when parsing JSON files, and the extension won't work correctly. It also opens the Output Channel when the button is clicked.

- Enabled the error to be thrown. By `throw`ing the error, we allow the extension to fail startup and crash at the point of parse errors.

This is to prevent further code that requires the parsed json from the `readJsonFile` function from throwing an unrelated error such as the "Cannot convert undefined or null to object" error, which makes it harder to debug. So if we fail the extension here, then we can easily debug the root cause.

Fixes the ts error from the workflow because I just forgot to commit it.

https://github.com/yCodeTech/auto-comment-blocks/actions/runs/19952456507/job/57215155157?pr=15

- Added new `showChannel` method to logger to show the Output Channel.